From: Florian Müllner Date: Sat, 26 Nov 2016 18:32:22 +0000 (+0100) Subject: notificationDaemon: Keep source alive when replacing notification X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~1013^2^2~618 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=accd24e379374b202791af2b3e065e1fca4fa406;p=gnome-shell.git notificationDaemon: Keep source alive when replacing notification When a GNotification has the same ID as a previous one, it should be shown as a new notification after withdrawing the old one. However for this to work, we must not destroy the corresponding source if withdrawing the old notification lets the notification count drop to zero, so make sure the source is kept alive until the replace operation has completed. https://bugzilla.gnome.org/show_bug.cgi?id=775149 --- diff --git a/js/ui/notificationDaemon.js b/js/ui/notificationDaemon.js index 120751bde..24c82b35f 100644 --- a/js/ui/notificationDaemon.js +++ b/js/ui/notificationDaemon.js @@ -690,6 +690,7 @@ const GtkNotificationDaemonAppSource = new Lang.Class({ throw new InvalidAppError(); this._notifications = {}; + this._notificationPending = false; this.parent(this._app.get_name()); }, @@ -729,6 +730,8 @@ const GtkNotificationDaemonAppSource = new Lang.Class({ }, addNotification: function(notificationId, notificationParams, showBanner) { + this._notificationPending = true; + if (this._notifications[notificationId]) this._notifications[notificationId].destroy(); @@ -742,6 +745,14 @@ const GtkNotificationDaemonAppSource = new Lang.Class({ this.notify(notification); else this.pushNotification(notification); + + this._notificationPending = false; + }, + + destroy: function(reason) { + if (this._notificationPending) + return; + this.parent(reason); }, removeNotification: function(notificationId) {